Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b99b5a19a5dc9a5b1e3537721c4a5b73c2cf1ed62150183b9f30caddfd34052

Tx prefix hash: a477fb6e80794828cb6a025b960793aea55b0d90efa0f1720eda8849972723ab
Tx public key: 99e965971645cec363727fbf0fd83acf67d78dcf414b12f2bd313742fd847d21
Timestamp: 1731782642 Timestamp [UCT]: 2024-11-16 18:44:02 Age [y:d:h:m:s]: 00:164:15:51:55
Block: 1155137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117559 RingCT/type: yes/0
Extra: 0199e965971645cec363727fbf0fd83acf67d78dcf414b12f2bd313742fd847d2102110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6d211d3f7787760d4be63010a1025f0d5bf23ed382ad5b7e51c7b11a723d753 0.600000000000 1640752 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": 1155147, "vin": [ { "gen": { "height": 1155137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6d211d3f7787760d4be63010a1025f0d5bf23ed382ad5b7e51c7b11a723d753" } } ], "extra": [ 1, 153, 233, 101, 151, 22, 69, 206, 195, 99, 114, 127, 191, 15, 216, 58, 207, 103, 215, 141, 207, 65, 75, 18, 242, 189, 49, 55, 66, 253, 132, 125, 33, 2, 17, 0, 0, 0, 12, 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