Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 799572419dc8385d6143d296500d3f466a6b3cb90ef5efc0dd7219ef4dcf1f8d

Tx prefix hash: f07bd325e6b5a284176ff41282af3835eed059f30fb4c2b08e11bf361c898e44
Tx public key: 62ec800393c8b06185c06139095ef61b144f60d66327e4df52ebf93e76a356d1
Timestamp: 1724653023 Timestamp [UCT]: 2024-08-26 06:17:03 Age [y:d:h:m:s]: 01:073:23:46:28
Block: 1096118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311335 RingCT/type: yes/0
Extra: 0162ec800393c8b06185c06139095ef61b144f60d66327e4df52ebf93e76a356d102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21c12ebdd530c08e1f6c5740b4b1def9eba274e7583cbde03a4e9e85a609a6d8 0.600000000000 1571305 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": 1096128, "vin": [ { "gen": { "height": 1096118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21c12ebdd530c08e1f6c5740b4b1def9eba274e7583cbde03a4e9e85a609a6d8" } } ], "extra": [ 1, 98, 236, 128, 3, 147, 200, 176, 97, 133, 192, 97, 57, 9, 94, 246, 27, 20, 79, 96, 214, 99, 39, 228, 223, 82, 235, 249, 62, 118, 163, 86, 209, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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