Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67c14d6fd4eea18e799f72059faea9aaa4ddcff20d72c0a15c4f5846c5c5d35e

Tx prefix hash: 5e3d0f70e073d511274a7ca19ef314fa0e105a96efa1273ca54f1f0dfb8aafb1
Tx public key: 82e9b5df80d6ef0099ba6e861950d1691f02f4e3cef4e1d1b6fab3f471793bb7
Timestamp: 1731280419 Timestamp [UCT]: 2024-11-10 23:13:39 Age [y:d:h:m:s]: 01:057:04:53:03
Block: 1150995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299366 RingCT/type: yes/0
Extra: 0182e9b5df80d6ef0099ba6e861950d1691f02f4e3cef4e1d1b6fab3f471793bb70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f11207ed5f34e47f1453e8f9216d58f3e8ce13bcf516055a1657d6c879fb4980 0.600000000000 1636444 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": 1151005, "vin": [ { "gen": { "height": 1150995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f11207ed5f34e47f1453e8f9216d58f3e8ce13bcf516055a1657d6c879fb4980" } } ], "extra": [ 1, 130, 233, 181, 223, 128, 214, 239, 0, 153, 186, 110, 134, 25, 80, 209, 105, 31, 2, 244, 227, 206, 244, 225, 209, 182, 250, 179, 244, 113, 121, 59, 183, 2, 17, 0, 0, 0, 1, 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