Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6113dcd197f91c47c28a36d03056ba73012fd153a4224bbf8ee922516cdfbfe8

Tx prefix hash: a4b2e6958cdf32bb4b9260f72f71c663b7a34a626c1eef1647fa3e86b4d43053
Tx public key: de2c0d50a85493745498a983352f8101fd1d6ba4f19f85ce66abe054c3e9cc79
Timestamp: 1722722335 Timestamp [UCT]: 2024-08-03 21:58:55 Age [y:d:h:m:s]: 00:241:21:22:00
Block: 1080125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172766 RingCT/type: yes/0
Extra: 01de2c0d50a85493745498a983352f8101fd1d6ba4f19f85ce66abe054c3e9cc7902110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c8530b0ff11fbc154a8a9fd72e12516a520d90a48edc65bcfb5bd34dd73d3e9 0.600000000000 1553366 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": 1080135, "vin": [ { "gen": { "height": 1080125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c8530b0ff11fbc154a8a9fd72e12516a520d90a48edc65bcfb5bd34dd73d3e9" } } ], "extra": [ 1, 222, 44, 13, 80, 168, 84, 147, 116, 84, 152, 169, 131, 53, 47, 129, 1, 253, 29, 107, 164, 241, 159, 133, 206, 102, 171, 224, 84, 195, 233, 204, 121, 2, 17, 0, 0, 0, 19, 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