Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e00469c8e1508b16268b1c9f1bef7e7b10ba014536f99e125b2489b492e7d557

Tx prefix hash: 1bdd75d9d88f7c4b49020c25328477d84b489e7a971698875fb2901293431dd7
Tx public key: 0e32b5767813498a9164a715e0b8af8ae89294ae15ff52809c257730a0632473
Timestamp: 1712968002 Timestamp [UCT]: 2024-04-13 00:26:42 Age [y:d:h:m:s]: 01:017:15:05:32
Block: 999233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273577 RingCT/type: yes/0
Extra: 010e32b5767813498a9164a715e0b8af8ae89294ae15ff52809c257730a063247302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59109da4a64d97e2c046787e7a8a1a37f7266112de1044c899d55e6811aa9afa 0.600000000000 1459711 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": 999243, "vin": [ { "gen": { "height": 999233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59109da4a64d97e2c046787e7a8a1a37f7266112de1044c899d55e6811aa9afa" } } ], "extra": [ 1, 14, 50, 181, 118, 120, 19, 73, 138, 145, 100, 167, 21, 224, 184, 175, 138, 232, 146, 148, 174, 21, 255, 82, 128, 156, 37, 119, 48, 160, 99, 36, 115, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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