Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533b7350519f225923fdb43c9828723538ae5f233a6ef9a7179310ef3bf3dd1c

Tx prefix hash: bc1015ef9c0f7dc445edc44e8a6ceab138953d02a139aec457c057ec16c1e5d7
Tx public key: 69373257b5184b4d7dc9e484a0e33cd32d73d38c3a41295f16f61374218f20e4
Timestamp: 1617106082 Timestamp [UCT]: 2021-03-30 12:08:02 Age [y:d:h:m:s]: 03:231:20:41:48
Block: 229689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925169 RingCT/type: yes/0
Extra: 0169373257b5184b4d7dc9e484a0e33cd32d73d38c3a41295f16f61374218f20e402110000000c3a645b90000000000000000000

1 output(s) for total of 106.400967406000 dcy

stealth address amount amount idx
00: 22c08c5af5925449a4f11b7f150e52ef7d0861f4e8db71ef533a4aae8c93e87c 106.400967406000 476669 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": 229699, "vin": [ { "gen": { "height": 229689 } } ], "vout": [ { "amount": 106400967406, "target": { "key": "22c08c5af5925449a4f11b7f150e52ef7d0861f4e8db71ef533a4aae8c93e87c" } } ], "extra": [ 1, 105, 55, 50, 87, 181, 24, 75, 77, 125, 201, 228, 132, 160, 227, 60, 211, 45, 115, 211, 140, 58, 65, 41, 95, 22, 246, 19, 116, 33, 143, 32, 228, 2, 17, 0, 0, 0, 12, 58, 100, 91, 144, 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