Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b1ca980882a2a33e71f4ce23d4f792c95ac33c62dbd7a6fbf4cc51f4067e7dd

Tx prefix hash: 2e08f417cc1907fb23df9f045fe55360e4e573f3eb61e136806fb7f629699ceb
Tx public key: 9d0ea7309b9452194c1381999228d1d78d24e172bcba0bfe912efa41a9565f4e
Timestamp: 1766099346 Timestamp [UCT]: 2025-12-18 23:09:06 Age [y:d:h:m:s]: 00:004:22:48:21
Block: 1436601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3540 RingCT/type: yes/0
Extra: 019d0ea7309b9452194c1381999228d1d78d24e172bcba0bfe912efa41a9565f4e0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 925411fb7c46368a89198843b3d6e5a241f2f291fffd4d29462ab4321e39e96c 0.600000000000 1925406 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": 1436611, "vin": [ { "gen": { "height": 1436601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "925411fb7c46368a89198843b3d6e5a241f2f291fffd4d29462ab4321e39e96c" } } ], "extra": [ 1, 157, 14, 167, 48, 155, 148, 82, 25, 76, 19, 129, 153, 146, 40, 209, 215, 141, 36, 225, 114, 188, 186, 11, 254, 145, 46, 250, 65, 169, 86, 95, 78, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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