Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3380b403a7afaaec1b658b44d6d909831b5dc9ce597a41851a37d74162c3fb

Tx prefix hash: 019a95f34c741b0f8fb1ae5b40794797e535a4d5bdca7ed867408140cfe9a524
Tx public key: 9a1b820d89e6ae0974721971753023e5e9171e0c6bdde191bdab57f402a02708
Timestamp: 1717405598 Timestamp [UCT]: 2024-06-03 09:06:38 Age [y:d:h:m:s]: 00:238:04:53:35
Block: 1036059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170215 RingCT/type: yes/0
Extra: 019a1b820d89e6ae0974721971753023e5e9171e0c6bdde191bdab57f402a0270802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab6f7e7177ac0bc99630070011d87edd665fb1eabdd3816d48c4438373d68ac 0.600000000000 1504584 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": 1036069, "vin": [ { "gen": { "height": 1036059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab6f7e7177ac0bc99630070011d87edd665fb1eabdd3816d48c4438373d68ac" } } ], "extra": [ 1, 154, 27, 130, 13, 137, 230, 174, 9, 116, 114, 25, 113, 117, 48, 35, 229, 233, 23, 30, 12, 107, 221, 225, 145, 189, 171, 87, 244, 2, 160, 39, 8, 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