Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ae307c10a476566aab096d0b3132e5727d74d0f42fe6af14c63bdacffcb8c5f

Tx prefix hash: 31508e322dfbd3fe8f293fe8e0e25560ce075a00b50dbe190054e0fe365819bb
Tx public key: 9e33b5a69a9ff40b92fabcc8c55fc9b3c38695ee0ceb98e872e0a8baf3361c75
Timestamp: 1719821873 Timestamp [UCT]: 2024-07-01 08:17:53 Age [y:d:h:m:s]: 00:256:15:12:56
Block: 1056078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183369 RingCT/type: yes/0
Extra: 019e33b5a69a9ff40b92fabcc8c55fc9b3c38695ee0ceb98e872e0a8baf3361c7502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44ccc95eb79c48273035cbeaad6af2df75e248d17f28dec3ca33917fabddb3a 0.600000000000 1526489 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": 1056088, "vin": [ { "gen": { "height": 1056078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44ccc95eb79c48273035cbeaad6af2df75e248d17f28dec3ca33917fabddb3a" } } ], "extra": [ 1, 158, 51, 181, 166, 154, 159, 244, 11, 146, 250, 188, 200, 197, 95, 201, 179, 195, 134, 149, 238, 12, 235, 152, 232, 114, 224, 168, 186, 243, 54, 28, 117, 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