Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccce670c4c605c031ae41ce66fb855712393b2fb2161a447838c8139321704f5

Tx prefix hash: 782327bc013439cf8cfc0ead66e0e8ba7a78014432a68f796ccc98a8e843fd64
Tx public key: 37713382d2e3e87deb4a23d12ebd5e517d3907490f4d5493f6dc885216f73f0f
Timestamp: 1714005411 Timestamp [UCT]: 2024-04-25 00:36:51 Age [y:d:h:m:s]: 01:037:22:38:00
Block: 1007854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288090 RingCT/type: yes/0
Extra: 0137713382d2e3e87deb4a23d12ebd5e517d3907490f4d5493f6dc885216f73f0f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09f2accec37e05b018a7d6c12b9c56da08f5993aed2b75546f361eb846ce76c6 0.600000000000 1469320 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": 1007864, "vin": [ { "gen": { "height": 1007854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09f2accec37e05b018a7d6c12b9c56da08f5993aed2b75546f361eb846ce76c6" } } ], "extra": [ 1, 55, 113, 51, 130, 210, 227, 232, 125, 235, 74, 35, 209, 46, 189, 94, 81, 125, 57, 7, 73, 15, 77, 84, 147, 246, 220, 136, 82, 22, 247, 63, 15, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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