Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0c4565120cfafbffb1edf307dea3f66d621204f88445fb7dbdaa6bad6eba2ef

Tx prefix hash: 9c0f8ceda0b9220728d5c1e1bf92325cf57f30c4b0d1992909dbb98b2878b181
Tx public key: 1364f8b0e20422c8ed67f8806669aad4b447a7b5b89762236f0b95df1f6138fe
Timestamp: 1722730342 Timestamp [UCT]: 2024-08-04 00:12:22 Age [y:d:h:m:s]: 00:243:01:55:35
Block: 1080191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173616 RingCT/type: yes/0
Extra: 011364f8b0e20422c8ed67f8806669aad4b447a7b5b89762236f0b95df1f6138fe021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a4eecfe0ebc4fd2fb090bc82164968e09fbd27f7312dccb7f00f830811af8f 0.600000000000 1553460 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": 1080201, "vin": [ { "gen": { "height": 1080191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a4eecfe0ebc4fd2fb090bc82164968e09fbd27f7312dccb7f00f830811af8f" } } ], "extra": [ 1, 19, 100, 248, 176, 226, 4, 34, 200, 237, 103, 248, 128, 102, 105, 170, 212, 180, 71, 167, 181, 184, 151, 98, 35, 111, 11, 149, 223, 31, 97, 56, 254, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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