Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34ff5808285c7c2ea735e48fb9f125b5c8c6ae869184100b1dee08ce3a3893b

Tx prefix hash: 2fca6e9d9d9961892d76236f0eba5671f6e83953d44342fc1c6c5f21b6a0b4b8
Tx public key: 930015255997a350d05a6cc920bf54f2786d386686cf37c4873fa84e0e7c8ae6
Timestamp: 1737833281 Timestamp [UCT]: 2025-01-25 19:28:01 Age [y:d:h:m:s]: 00:325:02:32:43
Block: 1205212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229923 RingCT/type: yes/0
Extra: 01930015255997a350d05a6cc920bf54f2786d386686cf37c4873fa84e0e7c8ae6021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39f81fbe58f4a53a79332187c08b28d10c88fba7995e3937a0964f5d21861ca5 0.600000000000 1691909 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": 1205222, "vin": [ { "gen": { "height": 1205212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39f81fbe58f4a53a79332187c08b28d10c88fba7995e3937a0964f5d21861ca5" } } ], "extra": [ 1, 147, 0, 21, 37, 89, 151, 163, 80, 208, 90, 108, 201, 32, 191, 84, 242, 120, 109, 56, 102, 134, 207, 55, 196, 135, 63, 168, 78, 14, 124, 138, 230, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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