Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63262fb1b29884197617dd1da117db9e08a5d325c7af948c5b202f5628dbe15a

Tx prefix hash: 48ecb33ce1a72bed08fd047be71d3c293a54c39c9979373084e052186ea6b0cf
Tx public key: f4f446ad21d21c7e0249a3c9812c8c2ef418b5867fd891b6384c20ec87f54cca
Timestamp: 1709768887 Timestamp [UCT]: 2024-03-06 23:48:07 Age [y:d:h:m:s]: 01:034:03:42:01
Block: 972738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285411 RingCT/type: yes/0
Extra: 01f4f446ad21d21c7e0249a3c9812c8c2ef418b5867fd891b6384c20ec87f54cca0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76525cb3b7a5b71f3bfd0d1d0d2a6a8e2775eea28d9eae65d2660b0e86d16fdd 0.600000000000 1432657 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": 972748, "vin": [ { "gen": { "height": 972738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76525cb3b7a5b71f3bfd0d1d0d2a6a8e2775eea28d9eae65d2660b0e86d16fdd" } } ], "extra": [ 1, 244, 244, 70, 173, 33, 210, 28, 126, 2, 73, 163, 201, 129, 44, 140, 46, 244, 24, 181, 134, 127, 216, 145, 182, 56, 76, 32, 236, 135, 245, 76, 202, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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