Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9b0a77a0756e75a3b76a490aafb17e9e6631292d24ade90d6cd7a808bf5cca6

Tx prefix hash: c0f7d943e02d35bd2a573d1cd28bf0eed40401da5b31ef21a6e5d75471a119c2
Tx public key: f4722cf59b5f29f05d5ae66f7405bc7eeb84ff7a0f41ab64c035969fae1a77eb
Timestamp: 1713722826 Timestamp [UCT]: 2024-04-21 18:07:06 Age [y:d:h:m:s]: 01:225:10:47:17
Block: 1005506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419813 RingCT/type: yes/0
Extra: 01f4722cf59b5f29f05d5ae66f7405bc7eeb84ff7a0f41ab64c035969fae1a77eb0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2bc44be4ace91a495251af039e1e915128263538068cecd63032c86a780e4dc 0.600000000000 1466224 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": 1005516, "vin": [ { "gen": { "height": 1005506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2bc44be4ace91a495251af039e1e915128263538068cecd63032c86a780e4dc" } } ], "extra": [ 1, 244, 114, 44, 245, 155, 95, 41, 240, 93, 90, 230, 111, 116, 5, 188, 126, 235, 132, 255, 122, 15, 65, 171, 100, 192, 53, 150, 159, 174, 26, 119, 235, 2, 17, 0, 0, 0, 5, 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