Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4055e4bceb67326a4af616936ebe76efa0c5aa99c5cb99f41ce3c409f321454

Tx prefix hash: 6e2b10848b9afccbe2ea460d2eefcce6fae1e01a7ddc8fd536173910278880e8
Tx public key: d6e64949646d0929ca2dadb92be1df6a220475ae2af4d754bdb92c2ce7c6eba0
Timestamp: 1726960013 Timestamp [UCT]: 2024-09-21 23:06:53 Age [y:d:h:m:s]: 01:017:15:45:40
Block: 1115260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270975 RingCT/type: yes/0
Extra: 01d6e64949646d0929ca2dadb92be1df6a220475ae2af4d754bdb92c2ce7c6eba0021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb18f46b05feea3f19c88ebd504db396275ae50613a69dd04e00e9083702493b 0.600000000000 1595331 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": 1115270, "vin": [ { "gen": { "height": 1115260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb18f46b05feea3f19c88ebd504db396275ae50613a69dd04e00e9083702493b" } } ], "extra": [ 1, 214, 230, 73, 73, 100, 109, 9, 41, 202, 45, 173, 185, 43, 225, 223, 106, 34, 4, 117, 174, 42, 244, 215, 84, 189, 185, 44, 44, 231, 198, 235, 160, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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