Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cfa2ba4eef7c5cb1a32fd62bcbb9a0f1e5687dcbbe8ba9207be01cb714b0ba6

Tx prefix hash: 91270823581e7f4b01fe0f1fd3c7fa510c2453e3b3fd0ccfc8ab75a7aa2d315b
Tx public key: e11138faad1ed74e09a642c07d976e5dc4b716de508ee80c29bf15b0ff4a21e4
Timestamp: 1712753535 Timestamp [UCT]: 2024-04-10 12:52:15 Age [y:d:h:m:s]: 01:204:01:22:02
Block: 997454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 404529 RingCT/type: yes/0
Extra: 01e11138faad1ed74e09a642c07d976e5dc4b716de508ee80c29bf15b0ff4a21e4

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6d081eae9142a321ba05a179e6d9f6d3755d2b0e8a0dce67e4e5dfad0f5622 0.600000000000 1457886 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": 997464, "vin": [ { "gen": { "height": 997454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6d081eae9142a321ba05a179e6d9f6d3755d2b0e8a0dce67e4e5dfad0f5622" } } ], "extra": [ 1, 225, 17, 56, 250, 173, 30, 215, 78, 9, 166, 66, 192, 125, 151, 110, 93, 196, 183, 22, 222, 80, 142, 232, 12, 41, 191, 21, 176, 255, 74, 33, 228 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8