Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4947ce1c6ab79a40512109fe155eaee4ef38e2c35c297d4203c3e6ea09b64a6

Tx prefix hash: 81410de1b8557a4d3fc04973a18ec746de9e06547eec3596a411710ad582b397
Tx public key: 468bd347850c9cb6c37050ae03309fdc8e67daca31b6d1849e90d5c7e382fbd0
Timestamp: 1737194118 Timestamp [UCT]: 2025-01-18 09:55:18 Age [y:d:h:m:s]: 00:151:15:48:45
Block: 1199952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108069 RingCT/type: yes/0
Extra: 01468bd347850c9cb6c37050ae03309fdc8e67daca31b6d1849e90d5c7e382fbd00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62926c32e6527cf7c0da9dd0b613c5500bf713768580517c54c322a1ab0fac4 0.600000000000 1686593 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": 1199962, "vin": [ { "gen": { "height": 1199952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62926c32e6527cf7c0da9dd0b613c5500bf713768580517c54c322a1ab0fac4" } } ], "extra": [ 1, 70, 139, 211, 71, 133, 12, 156, 182, 195, 112, 80, 174, 3, 48, 159, 220, 142, 103, 218, 202, 49, 182, 209, 132, 158, 144, 213, 199, 227, 130, 251, 208, 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