Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1a1bd9019de41a3ebfdd0db67faa208ea3c369332f6676a82cfbcd2d516ad0

Tx prefix hash: 309c3e64809b7f61ac82c40a0df91eefa0b4a6d2dc9659d491beb55ebc5d65cc
Tx public key: 5891283be17b5667d28d835035a78e1ef618940bde668934afefdf0c4e6519d2
Timestamp: 1717692182 Timestamp [UCT]: 2024-06-06 16:43:02 Age [y:d:h:m:s]: 01:172:21:35:36
Block: 1038423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382165 RingCT/type: yes/0
Extra: 015891283be17b5667d28d835035a78e1ef618940bde668934afefdf0c4e6519d202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5140b46cf85a7f3ed93455e2f76339e0eb698a4b9cc69a52ec657892ca0b9af 0.600000000000 1506984 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": 1038433, "vin": [ { "gen": { "height": 1038423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5140b46cf85a7f3ed93455e2f76339e0eb698a4b9cc69a52ec657892ca0b9af" } } ], "extra": [ 1, 88, 145, 40, 59, 225, 123, 86, 103, 210, 141, 131, 80, 53, 167, 142, 30, 246, 24, 148, 11, 222, 102, 137, 52, 175, 239, 223, 12, 78, 101, 25, 210, 2, 17, 0, 0, 0, 5, 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