Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3381e2a7831026aabafa2d9b7291b118da82c2c581243f03113a2f70f54f86c

Tx prefix hash: 2e85a0eb3ca69ae00cb287a284dc5c4f19c571ead23c2997ab614304f3a1db53
Tx public key: ba87c6d1cff9111a3c66621ff4e17e16269c7d8971d7189b4191953bfb5a97d8
Timestamp: 1735689716 Timestamp [UCT]: 2025-01-01 00:01:56 Age [y:d:h:m:s]: 00:103:00:19:32
Block: 1187496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73431 RingCT/type: yes/0
Extra: 01ba87c6d1cff9111a3c66621ff4e17e16269c7d8971d7189b4191953bfb5a97d8021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 646c88fac30412bb772555230c48c436177929b5198b3f0d0c9925d57e781cf0 0.600000000000 1673987 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": 1187506, "vin": [ { "gen": { "height": 1187496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646c88fac30412bb772555230c48c436177929b5198b3f0d0c9925d57e781cf0" } } ], "extra": [ 1, 186, 135, 198, 209, 207, 249, 17, 26, 60, 102, 98, 31, 244, 225, 126, 22, 38, 156, 125, 137, 113, 215, 24, 155, 65, 145, 149, 59, 251, 90, 151, 216, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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