Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382a3cbe792f097b7098af407539ffda4761f5dddb5be5b595d9e05602110dab

Tx prefix hash: 159a8a3617ac2964096a8c53086539f2edae52fe8ceed33130b8decd9d173fe0
Tx public key: 4f3bc96c78c89db7a8941e0fe246e67b6ead271309795bef57547a1c5f221896
Timestamp: 1741006590 Timestamp [UCT]: 2025-03-03 12:56:30 Age [y:d:h:m:s]: 00:263:03:59:45
Block: 1231244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185835 RingCT/type: yes/0
Extra: 014f3bc96c78c89db7a8941e0fe246e67b6ead271309795bef57547a1c5f221896021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca3cd5bf54b8e3aa044797372d03b6a2381d8e0f8345f8e2b8f4b6f59eb2875c 0.600000000000 1718151 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": 1231254, "vin": [ { "gen": { "height": 1231244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca3cd5bf54b8e3aa044797372d03b6a2381d8e0f8345f8e2b8f4b6f59eb2875c" } } ], "extra": [ 1, 79, 59, 201, 108, 120, 200, 157, 183, 168, 148, 30, 15, 226, 70, 230, 123, 110, 173, 39, 19, 9, 121, 91, 239, 87, 84, 122, 28, 95, 34, 24, 150, 2, 17, 0, 0, 0, 5, 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