Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ef76cf7fc75c4b0c8cdd9e07d618c6d8ac1209f274b2b0dd0847355c8bd79a

Tx prefix hash: afbcab1e9480c29f0315da43cb06dce4714ade70bd3ad953f479232f4c849232
Tx public key: 1f576bd6fb7be7accf8b27110a7f64ed23f53a06ed99d5efc450780103036e7d
Timestamp: 1713528504 Timestamp [UCT]: 2024-04-19 12:08:24 Age [y:d:h:m:s]: 00:364:14:34:07
Block: 1003898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260662 RingCT/type: yes/0
Extra: 011f576bd6fb7be7accf8b27110a7f64ed23f53a06ed99d5efc450780103036e7d021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b21d1971dcf6cca3f3738cefe2a59ce0ae19275ec26de227e426e8f84aa44d7 0.600000000000 1464448 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": 1003908, "vin": [ { "gen": { "height": 1003898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b21d1971dcf6cca3f3738cefe2a59ce0ae19275ec26de227e426e8f84aa44d7" } } ], "extra": [ 1, 31, 87, 107, 214, 251, 123, 231, 172, 207, 139, 39, 17, 10, 127, 100, 237, 35, 245, 58, 6, 237, 153, 213, 239, 196, 80, 120, 1, 3, 3, 110, 125, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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