Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 983153dd3fa8a59f5e05c3834691aa9161da11e9fe9dad16a81f0cf04c1128b4

Tx prefix hash: ad13205b2bb1f1e7a3fd75d5ec06ba78b7d77d58e61f8ada6c152b9863cce3b2
Tx public key: 3a556bd838ad0ebf1cb536b08f60ad8030a3257dcedc3064e276ba372acd1a0f
Timestamp: 1681145539 Timestamp [UCT]: 2023-04-10 16:52:19 Age [y:d:h:m:s]: 01:362:00:56:23
Block: 735675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520027 RingCT/type: yes/0
Extra: 013a556bd838ad0ebf1cb536b08f60ad8030a3257dcedc3064e276ba372acd1a0f02110000000133af99f4000000000000000000

1 output(s) for total of 2.240802374000 dcy

stealth address amount amount idx
00: e6e4e72a25f608f956c86b27df20440c003be06159aa1c0068c5ff0f91d2598f 2.240802374000 1182024 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": 735685, "vin": [ { "gen": { "height": 735675 } } ], "vout": [ { "amount": 2240802374, "target": { "key": "e6e4e72a25f608f956c86b27df20440c003be06159aa1c0068c5ff0f91d2598f" } } ], "extra": [ 1, 58, 85, 107, 216, 56, 173, 14, 191, 28, 181, 54, 176, 143, 96, 173, 128, 48, 163, 37, 125, 206, 220, 48, 100, 226, 118, 186, 55, 42, 205, 26, 15, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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