Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf63f83be5338b38aa918a5433b498adf8b33558a191f8a42a4789ab736c0ace

Tx prefix hash: 72e3b59110124102f7f8385d0badda1ed8f2dfd1d6750177559d1de86a9bd21f
Tx public key: 7c0066fecc29c3942410b6013e830e2999b6c72c76c455a9d25279db3af99257
Timestamp: 1731959527 Timestamp [UCT]: 2024-11-18 19:52:07 Age [y:d:h:m:s]: 00:118:10:11:57
Block: 1156603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84473 RingCT/type: yes/0
Extra: 017c0066fecc29c3942410b6013e830e2999b6c72c76c455a9d25279db3af992570211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6272109d68c10fcde38ba3d3c3bea0e3f3d266581b3366b7cb2830e830deedd6 0.600000000000 1642226 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": 1156613, "vin": [ { "gen": { "height": 1156603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6272109d68c10fcde38ba3d3c3bea0e3f3d266581b3366b7cb2830e830deedd6" } } ], "extra": [ 1, 124, 0, 102, 254, 204, 41, 195, 148, 36, 16, 182, 1, 62, 131, 14, 41, 153, 182, 199, 44, 118, 196, 85, 169, 210, 82, 121, 219, 58, 249, 146, 87, 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