Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a3f19700f8be73dbad9d38690a4766767e5ac1c7bd2190b6906933414e4ea5

Tx prefix hash: 4309a24288e62e81bcf924e2d1eb28a4ddfb471813865af04cb30d8b887e0fbf
Tx public key: 28f617c6b7df193e0963ca37a8d1171c8ce95d34ec8c36a2879660e4c081a815
Timestamp: 1736518894 Timestamp [UCT]: 2025-01-10 14:21:34 Age [y:d:h:m:s]: 00:067:20:55:53
Block: 1194364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48302 RingCT/type: yes/0
Extra: 0128f617c6b7df193e0963ca37a8d1171c8ce95d34ec8c36a2879660e4c081a8150211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7df126ed0a1c40a59d87b7b87176a9075da848b6be334c5aa0dee92b3a6664c 0.600000000000 1680933 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": 1194374, "vin": [ { "gen": { "height": 1194364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7df126ed0a1c40a59d87b7b87176a9075da848b6be334c5aa0dee92b3a6664c" } } ], "extra": [ 1, 40, 246, 23, 198, 183, 223, 25, 62, 9, 99, 202, 55, 168, 209, 23, 28, 140, 233, 93, 52, 236, 140, 54, 162, 135, 150, 96, 228, 192, 129, 168, 21, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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