Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30aede3ebba50db54c5268963dd7b87c9e23e9e2feda62f5be7986fd6c75b439

Tx prefix hash: 4dde005270fc43ec448f89ff7104749e146f7b7120d5ed67440c97f6219af93b
Tx public key: d2ff6c65add86a75e9e54a6b6ab2ef0a2a2b7e4716413496a580b4354ad19655
Timestamp: 1734998445 Timestamp [UCT]: 2024-12-24 00:00:45 Age [y:d:h:m:s]: 00:094:22:36:13
Block: 1181786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67629 RingCT/type: yes/0
Extra: 01d2ff6c65add86a75e9e54a6b6ab2ef0a2a2b7e4716413496a580b4354ad196550211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 302edf446f3c0fd49c6a64c70ea4e7c1a182cb92cca51136c01f6a5272dcef97 0.600000000000 1668213 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": 1181796, "vin": [ { "gen": { "height": 1181786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "302edf446f3c0fd49c6a64c70ea4e7c1a182cb92cca51136c01f6a5272dcef97" } } ], "extra": [ 1, 210, 255, 108, 101, 173, 216, 106, 117, 233, 229, 74, 107, 106, 178, 239, 10, 42, 43, 126, 71, 22, 65, 52, 150, 165, 128, 180, 53, 74, 209, 150, 85, 2, 17, 0, 0, 0, 3, 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