Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 240e31899e98963ed04f2f75e5b38ba880ab957d84e7574cc4ec06c74abc01dc

Tx prefix hash: df62b6195c31cb09771d4cd7f3c52c36c0d80e819ef144674577ff2deaa7ad9b
Tx public key: 8413525b5ced4e5d0c715551b563d9a6aa3793eeafcd57162f0cd85aad069243
Timestamp: 1737089436 Timestamp [UCT]: 2025-01-17 04:50:36 Age [y:d:h:m:s]: 00:056:21:12:13
Block: 1199086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40446 RingCT/type: yes/0
Extra: 018413525b5ced4e5d0c715551b563d9a6aa3793eeafcd57162f0cd85aad069243021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deac0980263f22d1b66ef8e2d087da76f7a818e3d2e22e86dc7b6d5f193250d4 0.600000000000 1685715 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": 1199096, "vin": [ { "gen": { "height": 1199086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deac0980263f22d1b66ef8e2d087da76f7a818e3d2e22e86dc7b6d5f193250d4" } } ], "extra": [ 1, 132, 19, 82, 91, 92, 237, 78, 93, 12, 113, 85, 81, 181, 99, 217, 166, 170, 55, 147, 238, 175, 205, 87, 22, 47, 12, 216, 90, 173, 6, 146, 67, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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