Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 116205f5332f14e7ce8e8bde42cd3586d26aad70b946386cfb548dcfe7f22d1a

Tx prefix hash: 093092fa9f9dc8df2c17dcd485a5181c4034f749f63436601dd0ad42f42b40ac
Tx public key: 7f426fd508a6aac431d916fa02b1c3fdb74a2b34c70e4798b0979ad576919a9a
Timestamp: 1717304690 Timestamp [UCT]: 2024-06-02 05:04:50 Age [y:d:h:m:s]: 01:169:07:28:27
Block: 1035220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379591 RingCT/type: yes/0
Extra: 017f426fd508a6aac431d916fa02b1c3fdb74a2b34c70e4798b0979ad576919a9a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c81e3b2624f59eeca7d18acfc32418ad50f3ff86f3f85e84eb78e8be0ec1dce 0.600000000000 1503741 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": 1035230, "vin": [ { "gen": { "height": 1035220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c81e3b2624f59eeca7d18acfc32418ad50f3ff86f3f85e84eb78e8be0ec1dce" } } ], "extra": [ 1, 127, 66, 111, 213, 8, 166, 170, 196, 49, 217, 22, 250, 2, 177, 195, 253, 183, 74, 43, 52, 199, 14, 71, 152, 176, 151, 154, 213, 118, 145, 154, 154, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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