Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b255e09e42cf8f30bd4314c5a3d77e155e36b163ea773fbf7155d0e77c71c85c

Tx prefix hash: 44e180e1d07596ccaaab5c6cfd0204721cd39f00033102b19cd65b8cca0122ce
Tx public key: 0eba3e65763b2e0fccf6304a4ba7267ea98e52e007df7e25dcdd8b4ffc17382d
Timestamp: 1735125725 Timestamp [UCT]: 2024-12-25 11:22:05 Age [y:d:h:m:s]: 00:083:22:42:05
Block: 1182840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59794 RingCT/type: yes/0
Extra: 010eba3e65763b2e0fccf6304a4ba7267ea98e52e007df7e25dcdd8b4ffc17382d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a260f68918c68796673b1cff5f1735435c14c08fbea8baf0bdd9bcaeba8b0fd5 0.600000000000 1669279 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": 1182850, "vin": [ { "gen": { "height": 1182840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a260f68918c68796673b1cff5f1735435c14c08fbea8baf0bdd9bcaeba8b0fd5" } } ], "extra": [ 1, 14, 186, 62, 101, 118, 59, 46, 15, 204, 246, 48, 74, 75, 167, 38, 126, 169, 142, 82, 224, 7, 223, 126, 37, 220, 221, 139, 79, 252, 23, 56, 45, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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