Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235dd0414ad6d07e74508080ee86b7873dac5c5a62b47950e29ca509b3f7f3fc

Tx prefix hash: c789c5189ccec75dc72e120ea188bf155c74a0f462c4b650174f9a6b6670e20b
Tx public key: 3e8ec7feb0e0cc4310a2dafa0b8653a1bff82240bd5c3debafb6deb6ad2d22b7
Timestamp: 1705932787 Timestamp [UCT]: 2024-01-22 14:13:07 Age [y:d:h:m:s]: 01:302:14:34:23
Block: 940892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475119 RingCT/type: yes/0
Extra: 013e8ec7feb0e0cc4310a2dafa0b8653a1bff82240bd5c3debafb6deb6ad2d22b70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6998eb9c9dec96791bffd7f644af2e5defc9aff8c40cad8d3758de9660cd81a2 0.600000000000 1399032 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": 940902, "vin": [ { "gen": { "height": 940892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6998eb9c9dec96791bffd7f644af2e5defc9aff8c40cad8d3758de9660cd81a2" } } ], "extra": [ 1, 62, 142, 199, 254, 176, 224, 204, 67, 16, 162, 218, 250, 11, 134, 83, 161, 191, 248, 34, 64, 189, 92, 61, 235, 175, 182, 222, 182, 173, 45, 34, 183, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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