Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1d669d9032781e3d049e1e378d67d0d52832bce61e77061680b5387e7e61b9

Tx prefix hash: be0dabc12a69069c99ffceac4b961fb35bcafbf74320e45eca881f866a93c881
Tx public key: 650974a5bfc91d27127ae81567201aced872ffd4f4773a5d8d5f276fac6e2c92
Timestamp: 1725193296 Timestamp [UCT]: 2024-09-01 12:21:36 Age [y:d:h:m:s]: 01:073:12:53:46
Block: 1100618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310992 RingCT/type: yes/0
Extra: 01650974a5bfc91d27127ae81567201aced872ffd4f4773a5d8d5f276fac6e2c9202110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd53c7d92515739968390421b854edf473b7ee42a190ab611ff4a8d4f281fc15 0.600000000000 1576597 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": 1100628, "vin": [ { "gen": { "height": 1100618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd53c7d92515739968390421b854edf473b7ee42a190ab611ff4a8d4f281fc15" } } ], "extra": [ 1, 101, 9, 116, 165, 191, 201, 29, 39, 18, 122, 232, 21, 103, 32, 26, 206, 216, 114, 255, 212, 244, 119, 58, 93, 141, 95, 39, 111, 172, 110, 44, 146, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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