Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61e9b9078098fbacc47f872246bbe1563f92f75ab7e436bdf401b6655602534

Tx prefix hash: 2d8b2a237c7033328bd10148298e4ad321791ad8be421e5661ff7378d4ed621a
Tx public key: c801e432b467f2c89bb70519a84c344f3a030d4ab84640984a57638e470b4bc9
Timestamp: 1700872188 Timestamp [UCT]: 2023-11-25 00:29:48 Age [y:d:h:m:s]: 00:332:18:43:50
Block: 898980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238330 RingCT/type: yes/0
Extra: 01c801e432b467f2c89bb70519a84c344f3a030d4ab84640984a57638e470b4bc9021100000004faf35c9c000000000000000000

1 output(s) for total of 0.644623391000 dcy

stealth address amount amount idx
00: 6ea0c4e888f8e94794902b8e395992f384866c3e9dfc457fe7e4f790160f99b0 0.644623391000 1355417 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": 898990, "vin": [ { "gen": { "height": 898980 } } ], "vout": [ { "amount": 644623391, "target": { "key": "6ea0c4e888f8e94794902b8e395992f384866c3e9dfc457fe7e4f790160f99b0" } } ], "extra": [ 1, 200, 1, 228, 50, 180, 103, 242, 200, 155, 183, 5, 25, 168, 76, 52, 79, 58, 3, 13, 74, 184, 70, 64, 152, 74, 87, 99, 142, 71, 11, 75, 201, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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