Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2723f0370215a5756e7f4aeaa829e160099be6a0c3dc04d7796add6031a5eb93

Tx prefix hash: 318bd84e3f9d027c8a17847b0778bf107c2512f200830f3d775de7cecb17c193
Tx public key: a9102191a1a2d568068d347662e83ebf1634a4236a7128603bd240c0a5297fcf
Timestamp: 1658385857 Timestamp [UCT]: 2022-07-21 06:44:17 Age [y:d:h:m:s]: 02:245:02:29:40
Block: 548386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696353 RingCT/type: yes/0
Extra: 01a9102191a1a2d568068d347662e83ebf1634a4236a7128603bd240c0a5297fcf021100000020d3fcec30000000000000000000

1 output(s) for total of 9.353403518000 dcy

stealth address amount amount idx
00: 14479f0a2cd089b69ea68c9347e6ae0ba15a2de99eb94b2b67c9cfc38a66333b 9.353403518000 979633 of 0

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": 548396, "vin": [ { "gen": { "height": 548386 } } ], "vout": [ { "amount": 9353403518, "target": { "key": "14479f0a2cd089b69ea68c9347e6ae0ba15a2de99eb94b2b67c9cfc38a66333b" } } ], "extra": [ 1, 169, 16, 33, 145, 161, 162, 213, 104, 6, 141, 52, 118, 98, 232, 62, 191, 22, 52, 164, 35, 106, 113, 40, 96, 59, 210, 64, 192, 165, 41, 127, 207, 2, 17, 0, 0, 0, 32, 211, 252, 236, 48, 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