Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad20b3ec65904f5a452004987c9d2916598a7d8583fa8ef0d057904ce20227b4

Tx prefix hash: 6de58e41b575bb926a03c5a7180c27e5a4cd1d0c00616f0d182cb38f59b72ac3
Tx public key: 0c0d5964cbdc0586a827da85d98c2b103e17d435cd693e5c9c25f9802a862f11
Timestamp: 1720656871 Timestamp [UCT]: 2024-07-11 00:14:31 Age [y:d:h:m:s]: 00:281:15:19:04
Block: 1063011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201227 RingCT/type: yes/0
Extra: 010c0d5964cbdc0586a827da85d98c2b103e17d435cd693e5c9c25f9802a862f1102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fffe12a63b331c6a813dfb17c48c687824e2c058fc40e69e9039d4a3bcc2e8d 0.600000000000 1533522 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": 1063021, "vin": [ { "gen": { "height": 1063011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fffe12a63b331c6a813dfb17c48c687824e2c058fc40e69e9039d4a3bcc2e8d" } } ], "extra": [ 1, 12, 13, 89, 100, 203, 220, 5, 134, 168, 39, 218, 133, 217, 140, 43, 16, 62, 23, 212, 53, 205, 105, 62, 92, 156, 37, 249, 128, 42, 134, 47, 17, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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