Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28942c83123318fe22edaeebf00d60f3e852e6b6c400732bd92adbf7eb0e7c8f

Tx prefix hash: 1563593bc495e38764b04075a9f3d731135051f6cdd9bf5bd9000bc923bddf56
Tx public key: d46a63401dbf018b3f05c5bc3dc3e7f5482dbf921f1981e74c504d1774f4a8ef
Timestamp: 1627575713 Timestamp [UCT]: 2021-07-29 16:21:53 Age [y:d:h:m:s]: 04:072:04:01:34
Block: 303263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1082413 RingCT/type: yes/0
Extra: 01d46a63401dbf018b3f05c5bc3dc3e7f5482dbf921f1981e74c504d1774f4a8ef021100000028e6f80b5a000000000000000000

1 output(s) for total of 60.697637711000 dcy

stealth address amount amount idx
00: a72d5d7456a079b976d0d8f53d2c2105c1b8314c9bdd284c3ce4476e1f07f2c8 60.697637711000 632998 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": 303273, "vin": [ { "gen": { "height": 303263 } } ], "vout": [ { "amount": 60697637711, "target": { "key": "a72d5d7456a079b976d0d8f53d2c2105c1b8314c9bdd284c3ce4476e1f07f2c8" } } ], "extra": [ 1, 212, 106, 99, 64, 29, 191, 1, 139, 63, 5, 197, 188, 61, 195, 231, 245, 72, 45, 191, 146, 31, 25, 129, 231, 76, 80, 77, 23, 116, 244, 168, 239, 2, 17, 0, 0, 0, 40, 230, 248, 11, 90, 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