Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6d54b26676cfa92b928a6a0422a6c30d120ea3c9fe53cfe4b9f19f09091ad0

Tx prefix hash: ec0764418a7628713ae8707d42a157af95002a8dff792120333c84a0ebba026d
Tx public key: 351c7e4f5ab3cb0fec90e46d65671b2bb797f8ea544b62e0becfb8b89f277b49
Timestamp: 1705396886 Timestamp [UCT]: 2024-01-16 09:21:26 Age [y:d:h:m:s]: 01:321:12:20:21
Block: 936472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488639 RingCT/type: yes/0
Extra: 01351c7e4f5ab3cb0fec90e46d65671b2bb797f8ea544b62e0becfb8b89f277b490211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d95229a421a06000ae7ef4647ca8254e92c0ece2893f361ac34bc53c2c75493 0.600000000000 1394500 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": 936482, "vin": [ { "gen": { "height": 936472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d95229a421a06000ae7ef4647ca8254e92c0ece2893f361ac34bc53c2c75493" } } ], "extra": [ 1, 53, 28, 126, 79, 90, 179, 203, 15, 236, 144, 228, 109, 101, 103, 27, 43, 183, 151, 248, 234, 84, 75, 98, 224, 190, 207, 184, 184, 159, 39, 123, 73, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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