Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0a8f57abaf0c4e048807082a92e56211fdf13864ba05583c1bafc9e4e45bb6

Tx prefix hash: e9d7dca43ec144f73ac37c034186ffdb141c82cd6b6f802e3f8836427985eae5
Tx public key: 1b57e0110b4d165eb7e1413f16890567eab1ffecdda8a74cb5ba816a80859bd6
Timestamp: 1717392207 Timestamp [UCT]: 2024-06-03 05:23:27 Age [y:d:h:m:s]: 00:286:21:32:35
Block: 1035947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205027 RingCT/type: yes/0
Extra: 011b57e0110b4d165eb7e1413f16890567eab1ffecdda8a74cb5ba816a80859bd602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a04b5d1068c845c19f8cf7f93da0b269b1c093c9ffff2a3731639ead6739f74 0.600000000000 1504472 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": 1035957, "vin": [ { "gen": { "height": 1035947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a04b5d1068c845c19f8cf7f93da0b269b1c093c9ffff2a3731639ead6739f74" } } ], "extra": [ 1, 27, 87, 224, 17, 11, 77, 22, 94, 183, 225, 65, 63, 22, 137, 5, 103, 234, 177, 255, 236, 221, 168, 167, 76, 181, 186, 129, 106, 128, 133, 155, 214, 2, 17, 0, 0, 0, 1, 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