Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fce9b3c5894c23819b8b640c964c64de2f1c0dc01ec1407dd47824cdad80e52

Tx prefix hash: e16b9a59af98d4a17d2c90aa762bae2c989246e88a497592480fce7d86d7e891
Tx public key: ffd3973f4dda2ee5261d77b3abce96ffa465e43f6799798c1dbfb734b4dca699
Timestamp: 1706763320 Timestamp [UCT]: 2024-02-01 04:55:20 Age [y:d:h:m:s]: 01:096:12:40:11
Block: 947797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330080 RingCT/type: yes/0
Extra: 01ffd3973f4dda2ee5261d77b3abce96ffa465e43f6799798c1dbfb734b4dca69902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16fd9ab30ef6510d09f671cc3c69ab11802dc1f26aafc0f83b68a0aa9ea88174 0.600000000000 1406155 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": 947807, "vin": [ { "gen": { "height": 947797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16fd9ab30ef6510d09f671cc3c69ab11802dc1f26aafc0f83b68a0aa9ea88174" } } ], "extra": [ 1, 255, 211, 151, 63, 77, 218, 46, 229, 38, 29, 119, 179, 171, 206, 150, 255, 164, 101, 228, 63, 103, 153, 121, 140, 29, 191, 183, 52, 180, 220, 166, 153, 2, 17, 0, 0, 0, 2, 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