Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 046c82371dafde332d1e46548ea17494393f23f01c1fd82efd17e461d78d90fb

Tx prefix hash: 0e9e23ef58160801eb8fa8c1c2c7aa41e114af52585ba45a6e52e091d0806661
Tx public key: 0e7c004ff0c71cc31acc5b7d2ab88c75f05df75356eca54fd29fcec0c23745ad
Timestamp: 1710056658 Timestamp [UCT]: 2024-03-10 07:44:18 Age [y:d:h:m:s]: 01:015:08:36:28
Block: 975135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271951 RingCT/type: yes/0
Extra: 010e7c004ff0c71cc31acc5b7d2ab88c75f05df75356eca54fd29fcec0c23745ad02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a92f1214169c9d2159fa0a758f07d43249c7fd00400b788436c25fa5fc1ec0b 0.600000000000 1435106 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": 975145, "vin": [ { "gen": { "height": 975135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a92f1214169c9d2159fa0a758f07d43249c7fd00400b788436c25fa5fc1ec0b" } } ], "extra": [ 1, 14, 124, 0, 79, 240, 199, 28, 195, 26, 204, 91, 125, 42, 184, 140, 117, 240, 93, 247, 83, 86, 236, 165, 79, 210, 159, 206, 192, 194, 55, 69, 173, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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