Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fc992b66c29464fda66b73b94782206806dc8c90060b7861f0be2a7c77feb2

Tx prefix hash: ede6071b352ab976d015362e65c60c3d2be8637d9917accc198eb935dff8eade
Tx public key: d1ff68adb596171c06bad09fb5c30372a5557a30258cf79b6c59cee88422ef82
Timestamp: 1737473407 Timestamp [UCT]: 2025-01-21 15:30:07 Age [y:d:h:m:s]: 00:147:02:53:18
Block: 1202225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104889 RingCT/type: yes/0
Extra: 01d1ff68adb596171c06bad09fb5c30372a5557a30258cf79b6c59cee88422ef820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4d2f22fff6d9b3688ea8f1bab4978fd0e3f5fb968d3c9195aa2a350c60d00b0 0.600000000000 1688888 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": 1202235, "vin": [ { "gen": { "height": 1202225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4d2f22fff6d9b3688ea8f1bab4978fd0e3f5fb968d3c9195aa2a350c60d00b0" } } ], "extra": [ 1, 209, 255, 104, 173, 181, 150, 23, 28, 6, 186, 208, 159, 181, 195, 3, 114, 165, 85, 122, 48, 37, 140, 247, 155, 108, 89, 206, 232, 132, 34, 239, 130, 2, 17, 0, 0, 0, 3, 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