Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e13ade6379424924e9e316ab6ca3123d98708c54cb16e7a074c46b80da97a545

Tx prefix hash: e425d79c04a1afd095dd6468c587c99a1bd5520f2e9afa595974e862b0a35fa1
Tx public key: 46c8f9c45778beeae24d7c17acf06583fa2ae4480603e19f4775ff74278b422a
Timestamp: 1731214137 Timestamp [UCT]: 2024-11-10 04:48:57 Age [y:d:h:m:s]: 00:129:17:16:54
Block: 1150447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92546 RingCT/type: yes/0
Extra: 0146c8f9c45778beeae24d7c17acf06583fa2ae4480603e19f4775ff74278b422a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a7dc6ae99be9c7d890cfdf0f9ed3a68e4855424ede159db8eb6315961a76587 0.600000000000 1635764 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": 1150457, "vin": [ { "gen": { "height": 1150447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a7dc6ae99be9c7d890cfdf0f9ed3a68e4855424ede159db8eb6315961a76587" } } ], "extra": [ 1, 70, 200, 249, 196, 87, 120, 190, 234, 226, 77, 124, 23, 172, 240, 101, 131, 250, 42, 228, 72, 6, 3, 225, 159, 71, 117, 255, 116, 39, 139, 66, 42, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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