Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f26c5f5cbca1fea275e4de9dc87755572b5aae89c03c05b0bc910a3dcd091b5

Tx prefix hash: 2bfb649b04898803eca1c13243cecb536a6002ff9a6cef360a7b0b0af6a37f50
Tx public key: 27093c82522015c958df18494ce55d12871a436b30b7cc825a32276e118723b3
Timestamp: 1711750986 Timestamp [UCT]: 2024-03-29 22:23:06 Age [y:d:h:m:s]: 00:363:20:35:19
Block: 989185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260128 RingCT/type: yes/0
Extra: 0127093c82522015c958df18494ce55d12871a436b30b7cc825a32276e118723b30211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bcb4a1dde276e0227c2553a3b8e4f9271cbce3604d09570b4332d51e55dbb6a 0.600000000000 1449480 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": 989195, "vin": [ { "gen": { "height": 989185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bcb4a1dde276e0227c2553a3b8e4f9271cbce3604d09570b4332d51e55dbb6a" } } ], "extra": [ 1, 39, 9, 60, 130, 82, 32, 21, 201, 88, 223, 24, 73, 76, 229, 93, 18, 135, 26, 67, 107, 48, 183, 204, 130, 90, 50, 39, 110, 17, 135, 35, 179, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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