Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 478199b680cc019b11ef781cd7f7a5eced685b7d6555769cd2d88668233bafc6

Tx prefix hash: fa619042a602738c297aebe5704058dfdcf617c0fd55864adb65468fda484adc
Tx public key: 77fc75df44ce0798ca4679b8c8cb91c6cb53ad6ac1ca0e1cd5ef7b0aa5866309
Timestamp: 1709266845 Timestamp [UCT]: 2024-03-01 04:20:45 Age [y:d:h:m:s]: 01:090:00:44:58
Block: 968576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325395 RingCT/type: yes/0
Extra: 0177fc75df44ce0798ca4679b8c8cb91c6cb53ad6ac1ca0e1cd5ef7b0aa58663090211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9aa620a0911e9e6942d946e6d902b5888d45073d379bcb26e4f683b71893cef 0.600000000000 1428393 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": 968586, "vin": [ { "gen": { "height": 968576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9aa620a0911e9e6942d946e6d902b5888d45073d379bcb26e4f683b71893cef" } } ], "extra": [ 1, 119, 252, 117, 223, 68, 206, 7, 152, 202, 70, 121, 184, 200, 203, 145, 198, 203, 83, 173, 106, 193, 202, 14, 28, 213, 239, 123, 10, 165, 134, 99, 9, 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