Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f95448c594d3a47a0a7d206d03f71800c400cd88b881c1878da81417981a54

Tx prefix hash: d13b105bb55e5c5b73cb2651def48b8b99e02facd475cfc3fa5816578d63e3d0
Tx public key: 0963fceec4efb8c8e980d85cb5d76cc58d3f437f6f378cefa24888c633671cd9
Timestamp: 1711140657 Timestamp [UCT]: 2024-03-22 20:50:57 Age [y:d:h:m:s]: 00:361:14:48:40
Block: 984126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258550 RingCT/type: yes/0
Extra: 010963fceec4efb8c8e980d85cb5d76cc58d3f437f6f378cefa24888c633671cd902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf97e2ccf4e7efaf65c13269cebdb1c0330eac663761dbeb9e8a5a2e1224aef5 0.600000000000 1444285 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": 984136, "vin": [ { "gen": { "height": 984126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf97e2ccf4e7efaf65c13269cebdb1c0330eac663761dbeb9e8a5a2e1224aef5" } } ], "extra": [ 1, 9, 99, 252, 238, 196, 239, 184, 200, 233, 128, 216, 92, 181, 215, 108, 197, 141, 63, 67, 127, 111, 55, 140, 239, 162, 72, 136, 198, 51, 103, 28, 217, 2, 17, 0, 0, 0, 6, 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