Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef2ef86a2ffe678590da639fb11c155ca5336ee1d7a9edb0b17d2fb090a4121e

Tx prefix hash: 130a673dfb55d562f1a6f529ca4f40d06b287fdffacb9eeb65c6087297ced0eb
Tx public key: 6708ff7889307f540db52f510b5775190e73ee1b197406d2bf1c17f8ec292807
Timestamp: 1577785805 Timestamp [UCT]: 2019-12-31 09:50:05 Age [y:d:h:m:s]: 05:038:07:01:43
Block: 35577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177192 RingCT/type: yes/0
Extra: 016708ff7889307f540db52f510b5775190e73ee1b197406d2bf1c17f8ec2928070211000000068a2ee0d9000000000000000000

1 output(s) for total of 467.863843684000 dcy

stealth address amount amount idx
00: d2eef3b83ceb6042bcac0a5710ae34d0f83dcf9c5c2c96d519834f5e8e41868b 467.863843684000 60074 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": 35587, "vin": [ { "gen": { "height": 35577 } } ], "vout": [ { "amount": 467863843684, "target": { "key": "d2eef3b83ceb6042bcac0a5710ae34d0f83dcf9c5c2c96d519834f5e8e41868b" } } ], "extra": [ 1, 103, 8, 255, 120, 137, 48, 127, 84, 13, 181, 47, 81, 11, 87, 117, 25, 14, 115, 238, 27, 25, 116, 6, 210, 191, 28, 23, 248, 236, 41, 40, 7, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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