Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9427cae05737607c8d8669ef29bf916581f9528119e84ced8c9266a194cc77

Tx prefix hash: 0ee4ee63c989639795d7b2769215cd41bbf65c9e84ce0a392897610ecfdcac2c
Tx public key: e2f45d81e9f7fd96163fd6335c0f4b99e2ae4d7e182c5aab37bd08185d28f2f5
Timestamp: 1680545894 Timestamp [UCT]: 2023-04-03 18:18:14 Age [y:d:h:m:s]: 02:235:09:34:50
Block: 731314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687536 RingCT/type: yes/0
Extra: 01e2f45d81e9f7fd96163fd6335c0f4b99e2ae4d7e182c5aab37bd08185d28f2f5021100000001b3164c24000000000000000000

1 output(s) for total of 2.316612341000 dcy

stealth address amount amount idx
00: 823787ff3f70873444320e63a3cc7038ba68ebe3f1bd229d175a0db2a18b008b 2.316612341000 1177079 of 0

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": 731324, "vin": [ { "gen": { "height": 731314 } } ], "vout": [ { "amount": 2316612341, "target": { "key": "823787ff3f70873444320e63a3cc7038ba68ebe3f1bd229d175a0db2a18b008b" } } ], "extra": [ 1, 226, 244, 93, 129, 233, 247, 253, 150, 22, 63, 214, 51, 92, 15, 75, 153, 226, 174, 77, 126, 24, 44, 90, 171, 55, 189, 8, 24, 93, 40, 242, 245, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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