Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95339d96af495be44cef757fdd7e70ee5ade3af1871ef75d7fc032bd5fba555e

Tx prefix hash: 285a28c63040f2de3ccc289d495af118cedde5993e7bbfffe379c2d63e9e4b8a
Tx public key: 2f2f54058fcc9d6d9d81e17062ed1add8d8884f9b268940f52574055f7f0730e
Timestamp: 1718106211 Timestamp [UCT]: 2024-06-11 11:43:31 Age [y:d:h:m:s]: 00:326:03:06:48
Block: 1041864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233070 RingCT/type: yes/0
Extra: 012f2f54058fcc9d6d9d81e17062ed1add8d8884f9b268940f52574055f7f0730e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd119c503618b7480a4da2d908ac2f735d8e8b8d53ab91afcf6763a1faffcf8 0.600000000000 1510639 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": 1041874, "vin": [ { "gen": { "height": 1041864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd119c503618b7480a4da2d908ac2f735d8e8b8d53ab91afcf6763a1faffcf8" } } ], "extra": [ 1, 47, 47, 84, 5, 143, 204, 157, 109, 157, 129, 225, 112, 98, 237, 26, 221, 141, 136, 132, 249, 178, 104, 148, 15, 82, 87, 64, 85, 247, 240, 115, 14, 2, 17, 0, 0, 0, 1, 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