Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c39195dcb5077039cfbf0b0a91a46fb0c099432dcf956df4cd77e5d0e2c4b6ab

Tx prefix hash: 2236095e96a6201c5d2170f10702230b8176b15936c3784f0d1e73e6d39de78f
Tx public key: c3c25c523e2eb4e9ddac3c536126c24838151f9e8e953ce2f774fcd92fea0441
Timestamp: 1713016625 Timestamp [UCT]: 2024-04-13 13:57:05 Age [y:d:h:m:s]: 01:207:21:11:05
Block: 999639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407249 RingCT/type: yes/0
Extra: 01c3c25c523e2eb4e9ddac3c536126c24838151f9e8e953ce2f774fcd92fea04410211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60ea9651c8313af04c3264a1da64cf409b3e75bc9f1257b827d55aa104f770f1 0.600000000000 1460121 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": 999649, "vin": [ { "gen": { "height": 999639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60ea9651c8313af04c3264a1da64cf409b3e75bc9f1257b827d55aa104f770f1" } } ], "extra": [ 1, 195, 194, 92, 82, 62, 46, 180, 233, 221, 172, 60, 83, 97, 38, 194, 72, 56, 21, 31, 158, 142, 149, 60, 226, 247, 116, 252, 217, 47, 234, 4, 65, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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