Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5263e7c47b299ef5e8065a8b693937d8e72b83360fadb5097260902586cc9d3b

Tx prefix hash: 39345fd91a73fa29f0586872f109304eae47eae268aadb75a4e884f8c9d6e00c
Tx public key: 358babf105e6d37d516c645ab6fdc87645c4e1b793417e377169da1ded73ce38
Timestamp: 1625505810 Timestamp [UCT]: 2021-07-05 17:23:30 Age [y:d:h:m:s]: 03:171:23:23:03
Block: 288774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 892818 RingCT/type: yes/0
Extra: 01358babf105e6d37d516c645ab6fdc87645c4e1b793417e377169da1ded73ce3802110000000a4b22f71d000000000000000000

1 output(s) for total of 67.791051327000 dcy

stealth address amount amount idx
00: bb81dc5d6558bd3b790b429f3ce613ab224de1d6271ae3a67cdbf0031c074f15 67.791051327000 604945 of 0

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": 288784, "vin": [ { "gen": { "height": 288774 } } ], "vout": [ { "amount": 67791051327, "target": { "key": "bb81dc5d6558bd3b790b429f3ce613ab224de1d6271ae3a67cdbf0031c074f15" } } ], "extra": [ 1, 53, 139, 171, 241, 5, 230, 211, 125, 81, 108, 100, 90, 182, 253, 200, 118, 69, 196, 225, 183, 147, 65, 126, 55, 113, 105, 218, 29, 237, 115, 206, 56, 2, 17, 0, 0, 0, 10, 75, 34, 247, 29, 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