Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63443c2348f4ddcbaf85f9b6fc02729d0bc1b82dd12d28fe0b10c0faedd08336

Tx prefix hash: 5375f5c071f0f8ae9e9d8838fbfe1ec92bb66134dcc22292b4a28794e5460430
Tx public key: 01460316ddaf3f46045b4510fb63d7983a4f7681bc3fa5f9cf9f71f175d8ef64
Timestamp: 1721192821 Timestamp [UCT]: 2024-07-17 05:07:01 Age [y:d:h:m:s]: 00:193:02:45:08
Block: 1067457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138120 RingCT/type: yes/0
Extra: 0101460316ddaf3f46045b4510fb63d7983a4f7681bc3fa5f9cf9f71f175d8ef6402110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8502e1b76d943b1a9cddd51f3e1923f52c9d31c0b3537b85873cf01e8ce033a9 0.600000000000 1538270 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": 1067467, "vin": [ { "gen": { "height": 1067457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8502e1b76d943b1a9cddd51f3e1923f52c9d31c0b3537b85873cf01e8ce033a9" } } ], "extra": [ 1, 1, 70, 3, 22, 221, 175, 63, 70, 4, 91, 69, 16, 251, 99, 215, 152, 58, 79, 118, 129, 188, 63, 165, 249, 207, 159, 113, 241, 117, 216, 239, 100, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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