Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a929d99cd3e2c3c56d2c8a3dd3b3023908d4699f1122b50e96dc574cda6b80

Tx prefix hash: 411ab4d83ee30a09aa6a309b41d08e5c0c195491df00403ee80628dee254ff1f
Tx public key: 87295081d70eb24f1efe1bc995f228a8fabab40bb1c68859bb1aeb74dc83e1a1
Timestamp: 1718436584 Timestamp [UCT]: 2024-06-15 07:29:44 Age [y:d:h:m:s]: 00:274:19:29:17
Block: 1044605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196370 RingCT/type: yes/0
Extra: 0187295081d70eb24f1efe1bc995f228a8fabab40bb1c68859bb1aeb74dc83e1a102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e00d326c3aa30bb8a03ee2bdc0062748295ffa775d8b940127c37b48b4a2024 0.600000000000 1513956 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": 1044615, "vin": [ { "gen": { "height": 1044605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e00d326c3aa30bb8a03ee2bdc0062748295ffa775d8b940127c37b48b4a2024" } } ], "extra": [ 1, 135, 41, 80, 129, 215, 14, 178, 79, 30, 254, 27, 201, 149, 242, 40, 168, 250, 186, 180, 11, 177, 198, 136, 89, 187, 26, 235, 116, 220, 131, 225, 161, 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