Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d2d2a4fe4b5825da80d88e79749ac4522c676e0f6e16e95696ba7bf051d495

Tx prefix hash: 137aca169999af0c058ca7914c227170cc456e7ae1e30ae8b5bfe4aaa6fcb2f6
Tx public key: 658c922aa162217ed65200cd3d33eec5459b5ef66b0b2cc8dd9010ecfa6f1a78
Timestamp: 1729994740 Timestamp [UCT]: 2024-10-27 02:05:40 Age [y:d:h:m:s]: 00:212:14:55:23
Block: 1140384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151791 RingCT/type: yes/0
Extra: 01658c922aa162217ed65200cd3d33eec5459b5ef66b0b2cc8dd9010ecfa6f1a78021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 971c5ee4112758c9d967c5b91ba4d23ce3e9107464a234aa17d698e8fd76a8a5 0.600000000000 1624179 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": 1140394, "vin": [ { "gen": { "height": 1140384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "971c5ee4112758c9d967c5b91ba4d23ce3e9107464a234aa17d698e8fd76a8a5" } } ], "extra": [ 1, 101, 140, 146, 42, 161, 98, 33, 126, 214, 82, 0, 205, 61, 51, 238, 197, 69, 155, 94, 246, 107, 11, 44, 200, 221, 144, 16, 236, 250, 111, 26, 120, 2, 17, 0, 0, 0, 4, 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