Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f929503047259789ad3cd4df6dd2bbfb27995768da1c59b938320a2151c44ffa

Tx prefix hash: 77a1200d0e6bca87033479f164f738b927c59eabe3c32cee3f352e212ae1a9de
Tx public key: 5b925396a831586fcccc53e059a77c6fbdce36d1ef0350525bf17e6816aa8a2f
Timestamp: 1710302952 Timestamp [UCT]: 2024-03-13 04:09:12 Age [y:d:h:m:s]: 01:028:18:40:41
Block: 977177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281541 RingCT/type: yes/0
Extra: 015b925396a831586fcccc53e059a77c6fbdce36d1ef0350525bf17e6816aa8a2f0211000000031c2d361c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03e6b6b6368ece4b69b9a1bec7fd813370e266cd4e6c553f1cdc9e3a7ba44812 0.600000000000 1437178 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": 977187, "vin": [ { "gen": { "height": 977177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03e6b6b6368ece4b69b9a1bec7fd813370e266cd4e6c553f1cdc9e3a7ba44812" } } ], "extra": [ 1, 91, 146, 83, 150, 168, 49, 88, 111, 204, 204, 83, 224, 89, 167, 124, 111, 189, 206, 54, 209, 239, 3, 80, 82, 91, 241, 126, 104, 22, 170, 138, 47, 2, 17, 0, 0, 0, 3, 28, 45, 54, 28, 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