Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809adb78c585548af987f3381f698b03c9539cd6791fc5f14747e2c8e349a403

Tx prefix hash: e2c9d6fd71cc87841039fdfcfce11eee88bf9d16cae07aeaa2fa5fd05fec867a
Tx public key: 687e7b8bb0a5b5d04586acd80585882bea2fa3fc660fd179d2f3a2326a3cad60
Timestamp: 1696694218 Timestamp [UCT]: 2023-10-07 15:56:58 Age [y:d:h:m:s]: 01:165:11:40:22
Block: 864543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379322 RingCT/type: yes/0
Extra: 01687e7b8bb0a5b5d04586acd80585882bea2fa3fc660fd179d2f3a2326a3cad60021100000006faf35c9c000000000000000000

1 output(s) for total of 0.838320695000 dcy

stealth address amount amount idx
00: cbc0948633288324d9732f974219df696726afb71fed8c1666c3f145100b6be6 0.838320695000 1319059 of 0

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": 864553, "vin": [ { "gen": { "height": 864543 } } ], "vout": [ { "amount": 838320695, "target": { "key": "cbc0948633288324d9732f974219df696726afb71fed8c1666c3f145100b6be6" } } ], "extra": [ 1, 104, 126, 123, 139, 176, 165, 181, 208, 69, 134, 172, 216, 5, 133, 136, 43, 234, 47, 163, 252, 102, 15, 209, 121, 210, 243, 162, 50, 106, 60, 173, 96, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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