Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0201e31cd5b9b383566bf0b09b3b3a0644e93c4ee0e5fdfdc92444ffe6369fda

Tx prefix hash: f42fa8d2bae95afe1966adaa38406d62a6bcf561801ff1ac50a89f22862e2c21
Tx public key: bfd0780d0953fb7d504e09883174ba48101f2245d7b13c68e7ae27d1547aca0c
Timestamp: 1729877129 Timestamp [UCT]: 2024-10-25 17:25:29 Age [y:d:h:m:s]: 00:169:14:46:55
Block: 1139404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121032 RingCT/type: yes/0
Extra: 01bfd0780d0953fb7d504e09883174ba48101f2245d7b13c68e7ae27d1547aca0c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f22046c9805a831275a906b806306936a85cbff002e0d4c116815726bbf6f5c 0.600000000000 1623191 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": 1139414, "vin": [ { "gen": { "height": 1139404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f22046c9805a831275a906b806306936a85cbff002e0d4c116815726bbf6f5c" } } ], "extra": [ 1, 191, 208, 120, 13, 9, 83, 251, 125, 80, 78, 9, 136, 49, 116, 186, 72, 16, 31, 34, 69, 215, 177, 60, 104, 231, 174, 39, 209, 84, 122, 202, 12, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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