Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f5c1807a232eaf20089eebeacde1f255afc3c24b46f957f35d714ec0989ce1

Tx prefix hash: 43d06bf0f6e0a1da97832b59e5f0ae945f2d05be7cc2013fa019a59fbe568f7d
Tx public key: f3f7243af96798fda0915798c3b1f2d55d51e96afc450354daf6ec4cf319b6df
Timestamp: 1736672405 Timestamp [UCT]: 2025-01-12 09:00:05 Age [y:d:h:m:s]: 00:157:14:10:39
Block: 1195636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112328 RingCT/type: yes/0
Extra: 01f3f7243af96798fda0915798c3b1f2d55d51e96afc450354daf6ec4cf319b6df0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e630c9fa4b785f9c5274c4bec3742d005491d7fc3fe17be8f854fb0561562cb 0.600000000000 1682227 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": 1195646, "vin": [ { "gen": { "height": 1195636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e630c9fa4b785f9c5274c4bec3742d005491d7fc3fe17be8f854fb0561562cb" } } ], "extra": [ 1, 243, 247, 36, 58, 249, 103, 152, 253, 160, 145, 87, 152, 195, 177, 242, 213, 93, 81, 233, 106, 252, 69, 3, 84, 218, 246, 236, 76, 243, 25, 182, 223, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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