Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45de9d15dec9dd4afa780c7676e6302de42cc7fd8ef5a78b35abbead1219e137

Tx prefix hash: 98730c16df7f393a39c786187840d274bdefb5c1471546250f52b02bc633ba1c
Tx public key: 04fb5653f9fa7f0bb1c9eb4f65eabacff8785a2125c0a1b1410fb45623f6315f
Timestamp: 1719600887 Timestamp [UCT]: 2024-06-28 18:54:47 Age [y:d:h:m:s]: 00:352:22:28:19
Block: 1054240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252145 RingCT/type: yes/0
Extra: 0104fb5653f9fa7f0bb1c9eb4f65eabacff8785a2125c0a1b1410fb45623f6315f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b2265a95212f3aa062a0635c095dcccc3c6fac7057b2c033b05dd437b1fc8fc 0.600000000000 1524601 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": 1054250, "vin": [ { "gen": { "height": 1054240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2265a95212f3aa062a0635c095dcccc3c6fac7057b2c033b05dd437b1fc8fc" } } ], "extra": [ 1, 4, 251, 86, 83, 249, 250, 127, 11, 177, 201, 235, 79, 101, 234, 186, 207, 248, 120, 90, 33, 37, 192, 161, 177, 65, 15, 180, 86, 35, 246, 49, 95, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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