Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e925789f581469f5045e6d311c55af75ac4b6c08bad3485c956583e5f9e55d5

Tx prefix hash: bba1732baf8918d551aa7987d9c7bc2b56f53905f25688d735e9fb7e04ffa177
Tx public key: dc8d2f88f13c814b79e372861d3ca27ef3c66bbc69a7d6c01b22886f0dd49549
Timestamp: 1736822458 Timestamp [UCT]: 2025-01-14 02:40:58 Age [y:d:h:m:s]: 00:341:05:10:33
Block: 1196880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241430 RingCT/type: yes/0
Extra: 01dc8d2f88f13c814b79e372861d3ca27ef3c66bbc69a7d6c01b22886f0dd495490211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ce388a38c7059bf32b6480b74042bc23234fbbdb3fd8c3c0266a153686e1f82 0.600000000000 1683485 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": 1196890, "vin": [ { "gen": { "height": 1196880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ce388a38c7059bf32b6480b74042bc23234fbbdb3fd8c3c0266a153686e1f82" } } ], "extra": [ 1, 220, 141, 47, 136, 241, 60, 129, 75, 121, 227, 114, 134, 29, 60, 162, 126, 243, 198, 107, 188, 105, 167, 214, 192, 27, 34, 136, 111, 13, 212, 149, 73, 2, 17, 0, 0, 0, 2, 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