Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad1e3c6109a1b7eef56b5cad992958b40dcc9f1fb736af812edea759ac8d6a0

Tx prefix hash: 96b3b33f68f735d23496214f24880565dc502677288bc07bb67ec0aa56132e58
Tx public key: 92a6dee84a3997a044d22f3af87a10b4f1c039aa9590d1c68e46f76e4e563dda
Timestamp: 1736086942 Timestamp [UCT]: 2025-01-05 14:22:22 Age [y:d:h:m:s]: 00:094:16:14:25
Block: 1190793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67450 RingCT/type: yes/0
Extra: 0192a6dee84a3997a044d22f3af87a10b4f1c039aa9590d1c68e46f76e4e563dda021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 010585f01d856f33bdc74f88f71bb0ed8fc9fac8e20d81965926918629edac0f 0.600000000000 1677312 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": 1190803, "vin": [ { "gen": { "height": 1190793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "010585f01d856f33bdc74f88f71bb0ed8fc9fac8e20d81965926918629edac0f" } } ], "extra": [ 1, 146, 166, 222, 232, 74, 57, 151, 160, 68, 210, 47, 58, 248, 122, 16, 180, 241, 192, 57, 170, 149, 144, 209, 198, 142, 70, 247, 110, 78, 86, 61, 218, 2, 17, 0, 0, 0, 3, 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