Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4cae01a81d5fc4ef190375ff04b75383cfc620e1e2ec9738d26fc62b625c43e

Tx prefix hash: ca6a4ad83b44878df9ae89cbb56814b29645b47100c4e648f6483b97c7082c98
Tx public key: 34a050c719c47e969a6b7c183653fb558c373fd87c9be9b1537987cd299d6d33
Timestamp: 1703501892 Timestamp [UCT]: 2023-12-25 10:58:12 Age [y:d:h:m:s]: 00:339:09:31:17
Block: 920775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243017 RingCT/type: yes/0
Extra: 0134a050c719c47e969a6b7c183653fb558c373fd87c9be9b1537987cd299d6d3302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2998b8ab59f46e244b2bf1c79f2e23c2f88e0813e2a45433d58f3b4970822529 0.600000000000 1378459 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": 920785, "vin": [ { "gen": { "height": 920775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2998b8ab59f46e244b2bf1c79f2e23c2f88e0813e2a45433d58f3b4970822529" } } ], "extra": [ 1, 52, 160, 80, 199, 25, 196, 126, 150, 154, 107, 124, 24, 54, 83, 251, 85, 140, 55, 63, 216, 124, 155, 233, 177, 83, 121, 135, 205, 41, 157, 109, 51, 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