Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a0299e7e09d37c0da474bca115e8061b1ca27cd488c9a32653feab50ac150a6d

Tx prefix hash: 1bb7cdc8619bfd1cc70fe91c5cfe39d325b57dad82d6ee173f9527d30b906b1d
Tx public key: 8951a80cbdef8dfc11685b7e9f1c5a9f22d0174d4a868dbb2ba497c2ed3b70bf
Timestamp: 1751553921 Timestamp [UCT]: 2025-07-03 14:45:21 Age [y:d:h:m:s]: 00:132:21:40:43
Block: 1318011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93216 RingCT/type: yes/0
Extra: 018951a80cbdef8dfc11685b7e9f1c5a9f22d0174d4a868dbb2ba497c2ed3b70bf02110000001043846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a5e421808d3f80d96d4f7a935ab35884b205e26e81801410f60ca16f587883a 0.600000000000 1805682 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1318021, "vin": [ { "gen": { "height": 1318011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a5e421808d3f80d96d4f7a935ab35884b205e26e81801410f60ca16f587883a" } } ], "extra": [ 1, 137, 81, 168, 12, 189, 239, 141, 252, 17, 104, 91, 126, 159, 28, 90, 159, 34, 208, 23, 77, 74, 134, 141, 187, 43, 164, 151, 194, 237, 59, 112, 191, 2, 17, 0, 0, 0, 16, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8