Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060e2c7e4ca30d39bf48e9d865dc33fd98a74f8dc54542b749ddfd49be5d66d3

Tx prefix hash: 945dd713ffb6e21256861d310e5a74bd4d4a441393bcd27f654f72d1349411b3
Tx public key: 68aba893bbdf7926d6cddf1063efa596175104c685318807d54b7ea5f88cb0d6
Timestamp: 1707059655 Timestamp [UCT]: 2024-02-04 15:14:15 Age [y:d:h:m:s]: 01:102:04:10:35
Block: 950258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334112 RingCT/type: yes/0
Extra: 0168aba893bbdf7926d6cddf1063efa596175104c685318807d54b7ea5f88cb0d60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb6189897d7a82d2ab446d02009a3a0e6ccf1da3129cd3228cc1545557c4d49f 0.600000000000 1408846 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": 950268, "vin": [ { "gen": { "height": 950258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb6189897d7a82d2ab446d02009a3a0e6ccf1da3129cd3228cc1545557c4d49f" } } ], "extra": [ 1, 104, 171, 168, 147, 187, 223, 121, 38, 214, 205, 223, 16, 99, 239, 165, 150, 23, 81, 4, 198, 133, 49, 136, 7, 213, 75, 126, 165, 248, 140, 176, 214, 2, 17, 0, 0, 0, 2, 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