Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4279168b4c6befe7a061cdeeee5558a0cf4665b6004f1d975ae40e15a4388a48

Tx prefix hash: f6801c7cf65d743a2a5aca37e8019601dd338b1872147ea5d1f36d9b1f434504
Tx public key: 0fdf479a272b765c792eacd59e625e9af4524bba4b872c342a31c4518129fdb6
Timestamp: 1715532948 Timestamp [UCT]: 2024-05-12 16:55:48 Age [y:d:h:m:s]: 01:016:22:48:08
Block: 1020553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273023 RingCT/type: yes/0
Extra: 010fdf479a272b765c792eacd59e625e9af4524bba4b872c342a31c4518129fdb602110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11127d4503452c8f3889a63f4f771208d4a17f9d0d278a0a0b31938b09fb8c18 0.600000000000 1484634 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": 1020563, "vin": [ { "gen": { "height": 1020553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11127d4503452c8f3889a63f4f771208d4a17f9d0d278a0a0b31938b09fb8c18" } } ], "extra": [ 1, 15, 223, 71, 154, 39, 43, 118, 92, 121, 46, 172, 213, 158, 98, 94, 154, 244, 82, 75, 186, 75, 135, 44, 52, 42, 49, 196, 81, 129, 41, 253, 182, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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