Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9536ce0db53ff083e49dbe2b53de3b91a947fae2b869cfa32022c5a1e871bd6d

Tx prefix hash: 175a31031a80a1b4673f45223283608506a8b6131eca90b00d0758d6da10b8d7
Tx public key: 9224ebb4dadf3cd2d9ee69663fbce756d1c2b3c7f22ee59d20cbba497f0de38e
Timestamp: 1730038201 Timestamp [UCT]: 2024-10-27 14:10:01 Age [y:d:h:m:s]: 00:087:06:46:51
Block: 1140736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62363 RingCT/type: yes/0
Extra: 019224ebb4dadf3cd2d9ee69663fbce756d1c2b3c7f22ee59d20cbba497f0de38e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35a4d034d3fc45b894f666378078a830b42b67e9a4042d00c57ad93dfa1a07b3 0.600000000000 1624539 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": 1140746, "vin": [ { "gen": { "height": 1140736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35a4d034d3fc45b894f666378078a830b42b67e9a4042d00c57ad93dfa1a07b3" } } ], "extra": [ 1, 146, 36, 235, 180, 218, 223, 60, 210, 217, 238, 105, 102, 63, 188, 231, 86, 209, 194, 179, 199, 242, 46, 229, 157, 32, 203, 186, 73, 127, 13, 227, 142, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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