Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f561beb27c208fa7a108bf04e600ef84c3776fa0e147064abc85d7b100da689e

Tx prefix hash: 8432aaf68c3a6976102d289766c4e4ec15092fd717c6fa5ca00dbe9dc096c2a9
Tx public key: 98e92fca2f8d9c599ae26faaa6d514cb2d5917cf8871d26ec24c4d7a6deb06e7
Timestamp: 1724904914 Timestamp [UCT]: 2024-08-29 04:15:14 Age [y:d:h:m:s]: 00:222:05:54:41
Block: 1098217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158687 RingCT/type: yes/0
Extra: 0198e92fca2f8d9c599ae26faaa6d514cb2d5917cf8871d26ec24c4d7a6deb06e702110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ddd1beb309766642a066c9520fdeb3daf39bc537969c21e06825d97bca91dd7 0.600000000000 1573856 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": 1098227, "vin": [ { "gen": { "height": 1098217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ddd1beb309766642a066c9520fdeb3daf39bc537969c21e06825d97bca91dd7" } } ], "extra": [ 1, 152, 233, 47, 202, 47, 141, 156, 89, 154, 226, 111, 170, 166, 213, 20, 203, 45, 89, 23, 207, 136, 113, 210, 110, 194, 76, 77, 122, 109, 235, 6, 231, 2, 17, 0, 0, 0, 16, 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