Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f6d75056a2c293b4a85c44ece29435da1b2335775d3fdc3ddeff6ad50f5ee7d

Tx prefix hash: 73d068fe5873cf3b80e1eb7cd078e7a89dac4da8e747da85c0feef7e5196ce76
Tx public key: e5aef044340f76878cb86fb1ad7c7b6edb48dd6309ebb610b7f281e123e07444
Timestamp: 1728576956 Timestamp [UCT]: 2024-10-10 16:15:56 Age [y:d:h:m:s]: 01:029:18:32:56
Block: 1128663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279653 RingCT/type: yes/0
Extra: 01e5aef044340f76878cb86fb1ad7c7b6edb48dd6309ebb610b7f281e123e0744402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff90048ba10dacaaed326f35c995912a2ee162de9833d5e7ec231b0f454d1fbe 0.600000000000 1611482 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": 1128673, "vin": [ { "gen": { "height": 1128663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff90048ba10dacaaed326f35c995912a2ee162de9833d5e7ec231b0f454d1fbe" } } ], "extra": [ 1, 229, 174, 240, 68, 52, 15, 118, 135, 140, 184, 111, 177, 173, 124, 123, 110, 219, 72, 221, 99, 9, 235, 182, 16, 183, 242, 129, 225, 35, 224, 116, 68, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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