Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b347f0f83e4d02e9c9edebc10a9e2cee0bc57e40dceb6a74637a556a93ae3da

Tx prefix hash: d67713ba06d1fa6914dcc7281dc75833bf5862bf412f6038f9e184b1a31d18d9
Tx public key: b7e66a83345b894d12824cedb47c5079e8d217a86f57e86580ebe644c2e7f5bd
Timestamp: 1745652722 Timestamp [UCT]: 2025-04-26 07:32:02 Age [y:d:h:m:s]: 00:247:12:59:23
Block: 1269712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174689 RingCT/type: yes/0
Extra: 01b7e66a83345b894d12824cedb47c5079e8d217a86f57e86580ebe644c2e7f5bd02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 813b03dcf83260582d283b11c36a7d331316033575b2ba1f3260b73bc4d8efde 0.600000000000 1756951 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": 1269722, "vin": [ { "gen": { "height": 1269712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "813b03dcf83260582d283b11c36a7d331316033575b2ba1f3260b73bc4d8efde" } } ], "extra": [ 1, 183, 230, 106, 131, 52, 91, 137, 77, 18, 130, 76, 237, 180, 124, 80, 121, 232, 210, 23, 168, 111, 87, 232, 101, 128, 235, 230, 68, 194, 231, 245, 189, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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