Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb11be7fcda1bc2e0eeaf1902b58bf0130e322e74f40abb7e7457cd673a92a0f

Tx prefix hash: 448b837d0236bbce94ea468e12c10e8e1ca184b9220998c1bacdbd820df54ae9
Tx public key: f01ab3be58aaafb8af2b24482e5d768595ec70bab9b99111e9c50000adbd97b5
Timestamp: 1721110978 Timestamp [UCT]: 2024-07-16 06:22:58 Age [y:d:h:m:s]: 00:219:05:29:15
Block: 1066777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156556 RingCT/type: yes/0
Extra: 01f01ab3be58aaafb8af2b24482e5d768595ec70bab9b99111e9c50000adbd97b5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 794a74c562b67a60b7c77defe009d0e6ff2edc5b926a3ab77d3a65931b7845c4 0.600000000000 1537444 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": 1066787, "vin": [ { "gen": { "height": 1066777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "794a74c562b67a60b7c77defe009d0e6ff2edc5b926a3ab77d3a65931b7845c4" } } ], "extra": [ 1, 240, 26, 179, 190, 88, 170, 175, 184, 175, 43, 36, 72, 46, 93, 118, 133, 149, 236, 112, 186, 185, 185, 145, 17, 233, 197, 0, 0, 173, 189, 151, 181, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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