Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c295820e9e07927bd6d44df160878413f9510def27ffd2e97c3d2b7b4fd3759c

Tx prefix hash: e747fcf5ce471aaedb064a7408ebd7b3a87f26ac47606e44544e478d97905fd5
Tx public key: 90882fb0b900a32aecf999778ba5a36ef9f681463183e1cc4a25ee93ddec9d2f
Timestamp: 1705606020 Timestamp [UCT]: 2024-01-18 19:27:00 Age [y:d:h:m:s]: 01:151:00:00:03
Block: 938208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368942 RingCT/type: yes/0
Extra: 0190882fb0b900a32aecf999778ba5a36ef9f681463183e1cc4a25ee93ddec9d2f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4193fd8e67f1c03021e61e7b00b43dbc0328449c93c79968f229c5ced2b0cb5d 0.600000000000 1396278 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": 938218, "vin": [ { "gen": { "height": 938208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4193fd8e67f1c03021e61e7b00b43dbc0328449c93c79968f229c5ced2b0cb5d" } } ], "extra": [ 1, 144, 136, 47, 176, 185, 0, 163, 42, 236, 249, 153, 119, 139, 165, 163, 110, 249, 246, 129, 70, 49, 131, 225, 204, 74, 37, 238, 147, 221, 236, 157, 47, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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