Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c39b6ad5e62fdf068ba2f41fe20a9f9c213b31850764c835045dcc2972e328cd

Tx prefix hash: 494cf4388508e2f53e8f74434d4d2bd893a793103b2487b7af6ae7efb13834d8
Tx public key: 55c7bb4bce272befbca2af18cc836dbdce0e50bfc43b0acc99d33709ac69fe26
Timestamp: 1715233912 Timestamp [UCT]: 2024-05-09 05:51:52 Age [y:d:h:m:s]: 00:188:05:46:03
Block: 1018046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134745 RingCT/type: yes/0
Extra: 0155c7bb4bce272befbca2af18cc836dbdce0e50bfc43b0acc99d33709ac69fe2602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6f7d172011620504513bea8a7b56abaf7e3d79f213dc2b0aa6d97ca175f614 0.600000000000 1481831 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": 1018056, "vin": [ { "gen": { "height": 1018046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6f7d172011620504513bea8a7b56abaf7e3d79f213dc2b0aa6d97ca175f614" } } ], "extra": [ 1, 85, 199, 187, 75, 206, 39, 43, 239, 188, 162, 175, 24, 204, 131, 109, 189, 206, 14, 80, 191, 196, 59, 10, 204, 153, 211, 55, 9, 172, 105, 254, 38, 2, 17, 0, 0, 0, 6, 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